Skip to main content

This is a new service – your feedback will help us to improve it.

Calderdale Metropolitan Borough Council

Tree preservation zone

There is a problem

  • 564 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Trees at Gratrix Lane and Wood Nook Lane, Sowerby Bridge.

reference
04/01259/C/1
name
Trees at Gratrix Lane and Wood Nook Lane, Sowerby Bridge.
tree-preservation-order

undefined

04/01259/C
tree-preservation-zone-type
woodland
geometry
MULTIPOLYGON (((-1.904428 53.714014,-1.904492 53.713926,-1.904435 53.713928,-1.904500 53.713828,-1.904448 53.713805,-1.904657 53.713617,-1.904716 53.713643,-1.904716 53.713662,-1.904854 53.713691,-1.904966 53.713377,-1.904970 53.713352,-1.904979 53.713321,-1.904989 53.713254,-1.904946 53.713252,-1.904927 53.713256,-1.904865 53.713254,-1.904859 53.713250,-1.904847 53.713222,-1.904818 53.713222,-1.904773 53.713241,-1.904769 53.713249,-1.904749 53.713307,-1.904739 53.713346,-1.904728 53.713422,-1.904696 53.713510,-1.904690 53.713521,-1.904578 53.713675,-1.904148 53.713692,-1.904174 53.713851,-1.904178 53.713867,-1.904197 53.714010,-1.904225 53.714009,-1.904227 53.714025,-1.904428 53.714014)),((-1.904472 53.714392,-1.904452 53.714359,-1.904420 53.714360,-1.904418 53.714350,-1.904205 53.714428,-1.904278 53.714428,-1.904794 53.714479,-1.904849 53.714487,-1.904943 53.714504,-1.905113 53.714541,-1.905154 53.714547,-1.905180 53.714549,-1.905212 53.714544,-1.905264 53.714533,-1.905298 53.714522,-1.905311 53.714515,-1.905331 53.714498,-1.905358 53.714465,-1.905362 53.714456,-1.905448 53.714363,-1.905457 53.714350,-1.905533 53.714207,-1.905629 53.714015,-1.905635 53.714000,-1.905639 53.713996,-1.905651 53.713974,-1.905661 53.713962,-1.905681 53.713932,-1.905800 53.713746,-1.905900 53.713569,-1.905923 53.713523,-1.905978 53.713394,-1.905988 53.713359,-1.905997 53.713339,-1.906000 53.713327,-1.906056 53.713185,-1.906071 53.713132,-1.906097 53.713013,-1.906100 53.712968,-1.906100 53.712810,-1.906099 53.712799,-1.906024 53.712527,-1.906018 53.712524,-1.905994 53.712519,-1.905956 53.712514,-1.905888 53.712514,-1.905622 53.712563,-1.905543 53.712572,-1.905460 53.712575,-1.905466 53.712614,-1.905382 53.712618,-1.905358 53.712621,-1.905418 53.712764,-1.905682 53.712725,-1.905691 53.712741,-1.905904 53.712716,-1.906011 53.712964,-1.905969 53.712970,-1.905972 53.712975,-1.905972 53.712979,-1.905966 53.712988,-1.905950 53.712996,-1.905910 53.713004,-1.905879 53.713015,-1.905866 53.713027,-1.905865 53.713033,-1.905865 53.713036,-1.905890 53.713099,-1.905903 53.713098,-1.905918 53.713137,-1.905927 53.713184,-1.905877 53.713217,-1.905984 53.713242,-1.905904 53.713378,-1.905774 53.713350,-1.905780 53.713339,-1.905742 53.713337,-1.905730 53.713343,-1.905696 53.713562,-1.905111 53.713528,-1.905107 53.713546,-1.905064 53.713543,-1.905063 53.713554,-1.905015 53.713642,-1.905053 53.713728,-1.905085 53.713699,-1.905101 53.713690,-1.905109 53.713687,-1.905149 53.713679,-1.905168 53.713614,-1.905308 53.713615,-1.905282 53.713698,-1.905475 53.713755,-1.905462 53.713772,-1.905421 53.713806,-1.905395 53.713823,-1.905381 53.713829,-1.905368 53.713837,-1.905364 53.713848,-1.905362 53.713849,-1.905350 53.713867,-1.905342 53.713875,-1.905288 53.713921,-1.905278 53.713925,-1.905438 53.713962,-1.905437 53.713970,-1.905431 53.713981,-1.905370 53.714347,-1.905363 53.714351,-1.905354 53.714353,-1.905332 53.714353,-1.905326 53.714351,-1.905207 53.714342,-1.904882 53.714309,-1.904856 53.714304,-1.904802 53.714313,-1.904745 53.714347,-1.904595 53.714353,-1.904554 53.714397,-1.904472 53.714392)))
point
POINT (-1.905289 53.713623)
notes
Ash, beech, elm, hawthorn, sycamore
entry-date
2004-09-29
start-date
2004-09-29
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Calderdale Metropolitan Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL